Skip to content

chore: enable TSL strictBooleanExpressions and sync sample rules - #1907

Merged
Rel1cx merged 1 commit into
mainfrom
chore/sync-samples-and-enable-tsl-strict-boolean
Jul 15, 2026
Merged

chore: enable TSL strictBooleanExpressions and sync sample rules#1907
Rel1cx merged 1 commit into
mainfrom
chore/sync-samples-and-enable-tsl-strict-boolean

Conversation

@Rel1cx

@Rel1cx Rel1cx commented Jul 15, 2026

Copy link
Copy Markdown
Owner
  • Enable TSL core rules in .pkgs/configs/tsl.config.base.{js,ts}
    • ...core.all()
    • core.strictBooleanExpressions with explicit nullable handling
    • Disable noConfusingVoidExpression, preferOptionalChain, switchExhaustivenessCheck
  • Update sample rule implementations in .pkgs/samples/src to satisfy strict boolean expressions
    • Replace truthy checks with explicit != null / == null
    • Remove decorative // ─ section comments
  • Sync updated sample code into migration guide MDX (apps/website/content/docs/migrating-from-eslint-plugin-react.mdx)
  • Update AST docs for getCalleeName description
  • Tighten null checks in packages/eslint/src/utils.ts and packages/core/src/jsx.test.ts

Update "[ ]" to "[x]" to check a box

What kind of change does this PR introduce?

Check at least one. If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers.

  • Bugfix
  • Feature
  • Perf
  • Docs
  • Test
  • Chore
  • Enhancement
  • New Binding issue #___
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change?

If yes, please describe the impact and migration path for existing applications in an attached issue.

  • Yes, and the changes were approved in issue #___
  • No

Checklist

  • When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
  • I have added a convincing reason for adding this feature, if necessary

Other information

- Enable TSL core rules in `.pkgs/configs/tsl.config.base.{js,ts}`
  - `...core.all()`
  - `core.strictBooleanExpressions` with explicit nullable handling
  - Disable `noConfusingVoidExpression`, `preferOptionalChain`,
    `switchExhaustivenessCheck`
- Update sample rule implementations in `.pkgs/samples/src` to satisfy
  strict boolean expressions
  - Replace truthy checks with explicit `!= null` / `== null`
  - Remove decorative `// ─` section comments
- Sync updated sample code into migration guide MDX
  (`apps/website/content/docs/migrating-from-eslint-plugin-react.mdx`)
- Update AST docs for `getCalleeName` description
- Tighten null checks in `packages/eslint/src/utils.ts` and
  `packages/core/src/jsx.test.ts`
@Rel1cx
Rel1cx marked this pull request as ready for review July 15, 2026 13:16
@vercel

vercel Bot commented Jul 15, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
eslint-react Building Building Preview, Comment Jul 15, 2026 1:16pm

@Rel1cx
Rel1cx merged commit b6d9c32 into main Jul 15, 2026
7 of 8 checks passed
@Rel1cx
Rel1cx deleted the chore/sync-samples-and-enable-tsl-strict-boolean branch July 15, 2026 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant